22 lines
1.6 KiB
Markdown
22 lines
1.6 KiB
Markdown
|
Robot Operating System (**ROS**) is not actually a traditional operating system like Windows or Linux. Instead, it is a flexible **middleware** framework—a collection of tools, libraries, and conventions designed to simplify the task of creating complex and robust robot behavior across a wide variety of robotic platforms.
|
||
|
|
|
||
|
|
The core philosophy of ROS is "don't reinvent the wheel." It allows roboticists to focus on their specific high-level logic while relying on community-tested packages for low-level tasks like motor control, sensor fusion, and navigation.
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Core Concepts: The Computation Graph
|
||
|
|
|
||
|
|
ROS operates on a "graph" architecture where different processes are represented as nodes. These nodes connect to each other to share information.
|
||
|
|
|
||
|
|
- **Nodes:** These are the basic building blocks. A node is a single process that performs a specific task (e.g., one node for the camera, one for path planning, one for wheel motors).
|
||
|
|
|
||
|
|
- **Messages:** Nodes communicate with each other by passing "messages." A message is a simple data structure, like an integer, a string, or a complex array of sensor data.
|
||
|
|
|
||
|
|
- **Topics:** This is the most common communication method (the **Publish/Subscribe** model). A node "publishes" a message to a specific topic (e.g., `/camera_images`), and any other node that needs that data "subscribes" to that topic.
|
||
|
|
|
||
|
|
- **Services:** Unlike the continuous stream of topics, services use a **Request/Response** model. One node sends a request (e.g., "Take a photo") and waits for the other node to send back a result.
|
||
|
|
|
||
|
|
|
||
|
|
> [!warning]
|
||
|
|
> The Above explanations is AI Generated, Learn more at : https://docs.ros.org/
|